I like the automatically opening the URL thing, but i don't like the "No such resource returned ..." thing, i prefer the skeleton. If you remove the that i will merge this PR.

do you think skeleton would make sense for the users who aint know whether their query fails or not.. or we can stop the loading skeleon if the query fails to do so.

Ok yeah, we should do this

• show the loading skeleton, in the loading state
• show nothing, in the error state

Since i want people to directly type in their queries and have the data fetched automatically, i don't want them to be bombarded with a "No such resource error".

yeah we can handle that by debouncing but yeah it is better to return a nothing.

Yeah but don't add debouncing. I want querying to feel extremely fast, deboucing will just add a delay. Since people are running the server on their own local machine, we don't care about how many times they hit the /query route. Debouncing would have made sense if we were calling an external API.

hmmm....makes sense , it is fixed by now